Hello lovely humans,

aegir just published its new version 9.1.2.

This version is covered by your current version range and after updating it in your project the build went from success to failure.

As aegir is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Of course this could just be a false positive, caused by a flaky test suite, or third parties that are currently broken or unavailable, but that would be another problem I’d recommend working on.

Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right?
Are you unsure about how things are supposed to work?

There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.

Good luck with your project ✨

You rock!

🌴

GitHub Release

Bug Fixes

• adjust loader config for webpack@2.1.0-beta.26 (bb04801)

The new version differs by 7 commits .

• e3a8617 chore: release version v9.1.2
• 5124bb7 chore: update contributors
• bb04801 fix: adjust loader config for webpack@2.1.0-beta.26
• 81ab16a chore: release version v9.1.1
• 089b370 chore: update contributors
• 10d6c15 fix(webpack): workaround for outdated http-browserify
• 368c5ba fix(test): remove webpack verbose logging

See the full diff.

This pull request was created by greenkeeper.io.

_{Tired of seeing this sponsor message? ⚡ greenkeeper upgrade}